<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Introduction</title>
<link rel="stylesheet" href="../boostbook.css" type="text/css">
<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
<link rel="home" href="../index.html" title="ODTONE 0.4">
<link rel="up" href="../index.html" title="ODTONE 0.4">
<link rel="prev" href="../index.html" title="ODTONE 0.4">
<link rel="next" href="getStart.html" title="Getting Started">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<table cellpadding="2" width="100%"><tr><td valign="top"><img alt="'ODTONE - Open Dot Twenty One'" width="100" height="100" src=".././images/logo.png"></td></tr></table>
<hr>
<div class="spirit-nav">
<a accesskey="p" href="../index.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="getStart.html"><img src="../images/next.png" alt="Next"></a>
</div>
<div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="odtone.intro"></a><a class="link" href="intro.html" title="Introduction">Introduction</a>
</h2></div></div></div>
<h4>
<a name="odtone.intro.h0"></a>
      <span><a name="odtone.intro.what_is_this_"></a></span><a class="link" href="intro.html#odtone.intro.what_is_this_">What
      is this?</a>
    </h4>
<p>
      ODTONE stands for Open Dot Twenty ONE and it is an open-source implementation
      of the Media Independent Handover framework from the IEEE 802.21 Media Independent
      Handover Services standard, using C++ APIs.
    </p>
<h4>
<a name="odtone.intro.h1"></a>
      <span><a name="odtone.intro.what_does_it_do_"></a></span><a class="link" href="intro.html#odtone.intro.what_does_it_do_">What
      does it do?</a>
    </h4>
<p>
      ODTONE supplies the implementation of a MIHF, supporting its inherent services
      (Media Independent Event Service (MIES), Media Independent Command Service
      (MIIS) and Media Independent Command Service (MICS), as well as supporting
      mechanisms (Capability Discovery, MIHF Registration, Event Registration, etc.).
      It also provides a set of APIs to enable ODTONE users to implement their own
      MIH-Users and Link SAPs and to interface with ODTONE's MIHF.
    </p>
<h4>
<a name="odtone.intro.h2"></a>
      <span><a name="odtone.intro.what_differences_can_be_found_regarding_other_ieee_802_21_implementations_"></a></span><a class="link" href="intro.html#odtone.intro.what_differences_can_be_found_regarding_other_ieee_802_21_implementations_">What
      differences can be found regarding other IEEE 802.21 implementations?</a>
    </h4>
<p>
      ODTONE aims to implement a MIHF that is capable of being deployed in multiple
      operating systems. In a first stage, it will support GNU/Linux, followed by
      Microsoft NT-based operating systems and others. This means this implementation
      will be decoupled of highly dependent operating system mechanisms.
    </p>
<h4>
<a name="odtone.intro.h3"></a>
      <span><a name="odtone.intro.what_does_this_mean_"></a></span><a class="link" href="intro.html#odtone.intro.what_does_this_mean_">What
      does this mean?</a>
    </h4>
<p>
      ODTONE's implementation aims to provide a MIHF that will work as a base for
      user's scenarios and which will enable the users to implement their own MIH_SAP
      and MIH_LINK_SAP. ODTONE provides a simple and flexible interface for the development
      of these SAPs, handling MIH Protocol messages and state transitions.
    </p>
<h4>
<a name="odtone.intro.h4"></a>
      <span><a name="odtone.intro.how_can_i_contribute_"></a></span><a class="link" href="intro.html#odtone.intro.how_can_i_contribute_">How
      can I contribute?</a>
    </h4>
<p>
      As was previously mentioned, ODTONE focuses on the MIHF and API's that will
      enable users to implement their own MIH_SAP and MIH_LINK_SAP. This means that
      it will be entirely up to the user to implement their MIH-Users and LINK technology
      support. We would be more than happy to known about your work on these matters!
    </p>
<h4>
<a name="odtone.intro.h5"></a>
      <span><a name="odtone.intro.changes_in_this_release"></a></span><a class="link" href="intro.html#odtone.intro.changes_in_this_release">Changes
      in this release</a>
    </h4>
<p>
      For changes from the previous release, please have a look at the <a class="link" href="changelog.html" title="Changelog">Changelog</a>
      section.
    </p>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
<td align="right"><div class="copyright-footer">Copyright &#169; 2009-2012 Universidade
      Aveiro<br>Copyright &#169; 2009-2012 Instituto
      de Telecomunica&#231;&#245;es - P&#243;lo Aveiro<p>
        This software is distributed under a license. The full license agreement
        can be found in the LICENSE in this distribution. This software may not be
        copied, modified, sold or distributed other than expressed in the named license
        agreement. This software is distributed without any warranty.
      </p>
</div></td>
</tr></table>
<hr>
<div class="spirit-nav">
<a accesskey="p" href="../index.html"><img src="../images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../images/home.png" alt="Home"></a><a accesskey="n" href="getStart.html"><img src="../images/next.png" alt="Next"></a>
</div>
</body>
</html>
